Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Routinator UI
This crate builds all the assets for the routinator web UI by storing them in a Vec of bytearrays that can be served by Hyper or another web serving crate.
The library has two public functions: get_endpoints()
, returning the Vec and
ui_resource(PATH)
that will return the UI resource.
Usage Example
use ;
const BASE_URL: &str = "/ui";
const CATCH_ALL_URL: &str = "index.html";
Building this Library
Please do not use cargo publish
directly on this crate, or bump the version of this create in Cargo.toml
manually!
All versioning (and code generation) is done automatically for this crate by its parent repository, the Vue App.
If you need to bump the version of this crate, git checkout
its parent at github
and issue:
npm version [major|minor|patch] -m <MESSAGE>
Where you can specify patch
, minor
or major
to bump the, well, patch, minor or major version respectively. This will take
care of the git (release) branches, the git tags, the version in Cargo.toml in this crate and the version in package.json of its
parent.
A new release, whether it is patch, minor or major will be deployed to routinator.nlnetlabs.nl
automatically by the github
Actions CI.
Using it locally
You can always refer to a local crate with the well-known mechanisms (including a { path = ".." }
argument in the Cargo.toml
line for this crate in routinator. If you make changes in the parent repo (the Vue App) and compile routinator, you should see
the local changes.
Also, a .tar.gz file is created for every push to the main
branch by github Actions and can be downloaded from there.